Enables you to specify the actual condition or the message from where the condition should be picked up for execution.Select one of the following options:

• None: This option is displayed by default. Select this option if you do not want to specify any execute condition.
  
• Static: Select Static option to specify the actual condition for execution. You can build a condition by clicking the XPath editor icon () appearing at the end of this field.
  
• Read from Message: Select Read from Message option to read the condition from the Process Specific Messages in the Message Map. This ensures that the business process does not have to be modified for every change. Click to build a condition.
  
  Note:
  
• Ensure that the Read from Message condition from the Message Map does not start with a slash.
  
• If a message contains an XPath expression, then the XPath need not be in single quotes. For example, if the message is /mycondition and it contains an expression as follows: GetEmployeeOutput/GetEmployeeResponse/tuple/old/Employees/City = "London", the XPath will be as follows: GetEmployeeOutput/GetEmployeeResponse/tuple/old/Employees/City = "London".
  In a Transaction construct, the Execute Condition option can be used instead of the Decision construct.You can view a small Decision icon on the left at the bottom of the construct to indicate that the activity includes a condition to be executed.

• Activity status: Records activity status, timestamp, user, etc. When you set the monitor level at this parameter, only the activity status is monitored. This helps in getting the updated activity status and to spot errors should the activity abort.
  
• Activity status, input and output messages: Records the input and output messages of the activity along with its status. When you set the monitor level at this parameter, the activity status and the input and output messages of the message map is monitored. This helps in tracking and spotting any error occurring at this level.
  
• Store complete activity information if activity aborts: Records activity status and input and output messages information only if the activity process aborts. If the activity is successfully completed, none of the monitoring information is recorded.